As you should already know this app will generate (to a BBEdit text file) serial/registration numbers (randomizing whenever possible) for various Macintosh software.
It should go without saying, but there always seems to be a few morons out there so i'll say it anyway:
••• DO NOT USE OR DISTRIBUTE THIS APP IN NON-ELITE ENVIRONMENTS… •••
••• DOING SO WILL ONLY RUIN IT FOR EVERYONE •••
••• THE FIRST TIME I HEAR OF A LEAK OF THIS APP WILL BE THE LAST •••
••• THINK ABOUT IT…ENOUGH SAID •••
I ask that you do not include numbers generated by this app (at least not in wholesale fashion) in other reference lists, since: A) This app generates different numbers (whenever possible) each time it is run so that there is no quick/painless counter measure to it; B) doing so would only help to counter its effectiveness (mainly by shortening the longevity of the SN# algorithms staying static); C) it would just increase the file size of the other lists while adding little value beyond the first number.
The date and time at which the output file was generated is now included at the start of the file -- this is the zero date that all the chronologically dependent algorithms use in their calculations.
The names specified for 'Owner Name' and 'Macintosh Name' in the 'Sharing Setup' control panel are now the first two user names used for generating serial numbers from. However this info is not saved to the 'Generated SN#s' file for security reasons -- instead you will see '<Sharing Owner Name>' and '<Sharing Machine Name>'. This change supports the few programs which require using the 'correct' user and/or machine name to fully enable themselves. (eg: the Dejal products)
Currently you must use a resource editor if you wish to change the user/company names (you may specify up to 20) that are used during generation. You may also change the number of copies to be licensed for (simultaneous users 1…9999, default is 10) and the number of serial numbers to generate (1…50 [this # is independent of the # of names you use], default is 3) for each product. These values are stored in 'STR#' resources that are labeled so that changing them is self explanatory. In a future release i'll probably get these from a seperate text file in order to make customizing easier.
Currently the generation of large tables is internally disabled (the only one currently implemented is for System's Twilight - for now I have included a seperate text file) -- in a future release I will make generation of these a configurable option.
Ocassionally you will see output of the form:
Illegal name: '<the illegal name>'
This only occurs when the given user name does not meet all the conditions placed upon it -- this is almost always due to the name being too short or containing only white space. (Don't be a moron -- using white space only, prefixed, or suffixed names is just dumb)
All of the serial number routines were tested with at least one number and usually more - however it is still possible that an error may have crept in, or a subtle point may have been missed during reverse engineering that only shows up some of the time --- so if you encounter an entry that doesn't work make sure you've got at least the given version of the product in question. If it still won't work complain with the complete details and it will (probably) get fixed.
If you have new or better algorithms (in some cases there is sufficient ambiguity [not always intended!] in the checking algorithm to allow multiple solutions to the inversion problem, with complete generality being the nicest but hardest to obtain) for current (ie: non-legacy) products feel free to submit them and a few examples of _known valid_ codes. (most useful would be C code that actually compiles - but intelligeble pseudo code will do)
Another item that would be useful is the actual _correct_ format of serial numbers for products which this app generates numbers for. (in the case of a discrepancy only -- most of the time it is possibly to fully invert the checking algorithm and thus obtain the format of the serial number, but not always, in which case a reasonable/arbitrary _working_ guess is made)
If there is some _current_ product you wish to see included here that _requires_ (ie: is dependent upon user name and/or number of copies or needs unique network serial numbers) a generator feel free to request it.
MISSION STATEMENT: Copy protection (CP) is an annoying nuisance that is ineffective. Serial number generators force software publishers to either: Accept the fact that their CP scheme is useless (possibly/hopefully abandoning it and the overhead of managing serial numbers) or; change their CP method/scheme and issue new serial numbers to their entire user-base for every release of their software. In this way the easy counter-counter-measure (of simply just checking for known elite name/password combos with each new release) that some authors (eg: Realmz's author) currently take is eliminated (since they won't know what names/numbers to target).
Future release versions will entirely supersede this release so there is _absolutely no need_ to keep old versions lying around.
Supported Products
===================
4D Online Help
Aladdin Desktop Tools
Apeiron
AXS Online Reader
Barrack
CalcWorks
CD Directory
Chiral
ColorSwitch
Compact Pro
Cyber Finder
DeBabelizer
Dejal QuickEncrypt
Dejal SndCataloguer
Dejal SndConverter Lite/Pro
Dejal SndPlayer
Dejal Text Utilities (TextConverter/TextMerge/TextSplitter)
Developer VISE
Developer VISE Lite
DiskDup Pro
DiskTools Collection
DiskTracker
Dome Wars
Eclipse
File Buddy
FontBox
Giza
GraphicConverter
Maelstrom
MathType
Now Bundle
Now Contact
Now Quick&Easy
Now UpToDate
Now Utilities
PowerBar Pro
Realmz
Realmz - Assault on Giant Mountain
Realmz - Castle in the Clouds
Realmz - Prelude to Pestilence
ScrapIt Pro
Smaller Installer
Snapz
SoundEdit 16
Stuffit Deluxe
Stuffit InstallerMaker
Swoop
Systems Twilight
TechTool Pro
Ultima III
UltraFind
Updater VISE
Versatile Pro
Miscellania for would be CP Reverse Engineers
=============================================
There a only a few basic non-keydisk, non-HW Dongle copy protection schemes in wide use:
1) Just a SN#/Reg Code (and possibly version#/id) that has certain
mathematical/string properties.
2) A Name/ID (given or enterable) field, a copies_Licensed field, version#,
and SN#/Reg Code which is derived by manipulating and combining the Name/ID
field and the copies_Licensed.
3) A time (date) based/limited SN#/Reg Code of type #1 or #2 above.
All of these protection schemes can in general be circumvented by a process of reverse engineering the SN# checking algorithm(s) during runtime (by using a debugger). In general you try to get an interrupt at or near the beginning of the SN# checking code (this step can require some insight - but 95% of the time placing a local ATrap break on GetIText, StringToNum, NumToString, DisposeDialog, HiliteControl, and/or ModalDialog will work). Once you find the start of the checking code you simply (or sometimes not so simply) symbolically disassemble the assembly code into pseudo or C code (I use a mixture myself). Ninety percent of the time you will see some code which reads in all the user input fields (possibly upper or lower casing them), checks to see if they are within a certain length and data type ranges (eg: Name>=4 chars with no digits, sn#=digits and >0). After these preliminaries you get to the actual heart of the method used. Typically you find code that does any/all of the following type of actions in various combinations:
A) Copy/Splice field(s) or subfield(s) to/into new variable(s). (ie BlockMove)
B) Convert a string/character (not necessarily numeric) to a numeric variable
via StringToNum or a custom conversion routine (often the base involved is
not 10 but a prime or power of 2 such as 8,16, and 32). [or, inversely
convert a number to a base b string]
C) Add/multiply/eor/ect... up the value of the characters in a string -
possibly including the length byte in the case of pascal strings.
D) Perform mathematical operations (often via library calls) such as integer
division (/), remainder upon integer division (mod,%), exclusive-oring
(xor,eor,^), oring (or,|), multiplication, addition, and subtraction. (note
be careful to observe the size and sign of the operations - ie byte, word,
long and signed or unsigned).
E) read/load in data from an internal table. (one table of $100 longwords is
particularily popular)
F) do 1 of n manipulations as selected by the value/state of some data.
G) loop over all or some of the elements in a string/number and perform any
of these actions for each element.
The last step in the SN# checking code is almost always the direct comparison of two values (usually longwords, but sometimes character strings) -- although sometimes the comparison is distributed throughout the checking algorithm calculation itself. Sometimes one these values is simply just the numerical value of your SN#, but more often the slightly indirect method of mangling both your SN#/reg code and all other fields into character string or numeric values and then comparing them is used. This second approach and generalizations upon it usually prove more difficult to invert in general -- as it requires reversing (at least partially inverting) a greater number of steps, often with more restrictions on intermediate values as opposed to restrictions on the terminal or input variables.
Version History
===============
1.0.8 (DNE yet… this is a 'to do' list for me)
-----
include arbitrary length longint library and implement generator for loanPro
1.0.7 (another minor update with some tweaking)
-----
added finder icons and balloon help string.
output TEXT files creator made user configurable. (change 'STR ' #128)
Added yet more generators still…
Conflict Catcher 3.x.x (3.0.4)
MultiClip Pro 3.2 (3.2alpha)
Ram Disk Saver 2.0.x (2.0)
URL Manager 1.1.x (1.1.4)
1.0.6 (added header time stamp and a few new generators)
-----
As a aid to maintenance I'm changing the format used to list new generators to include, in brackets, the latest version actually tested.
Added Generator for:
CalcWorks 1.5.x (1.5.1)
CD Directory 1.0.x (1.0.2)
FontBox 1.7.x (1.7.1) [only 3 unique SN#'s are possible per day]
SoundEdit 16 2.0.x (2.0)
1.0.5 (in case you were wondering 1.0.4 only lasted a couple of hours…)
-----
Changed some of the default names to coincide with the names that Bookworm is using so that it is easier to (further) verify my code against (a greater number of) known valid serial numbers.
Added Generator for:
DiskTracker 1.0.x (1.0.2)
1.0.4 (a few new generators plus major internal restructuring)
-----
Sharing Setup Owner/Machine names are now used as the first two user names.
Reordered output so products are listed in _mostly_ alphabetical order.
